home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Arsenal Files 6
/
The Arsenal Files 6 (Arsenal Computer).ISO
/
gen_bbs
/
aadd117b.zip
/
AUTOADD.DOC
< prev
next >
Wrap
Text File
|
1996-03-22
|
24KB
|
543 lines
AutoAdd V1.17
Copyright (C) 1995, 1996 David Blagburn
All rights reserved
What is AutoAdd? Well, AutoAdd is a bridge between Allfix and
PCBoard. Allfix allows automatic additions of new file areas but has
no way to let your BBS software (and consequently, your users) about
the new file area. This is where AutoAdd comes in. AutoAdd will:
* Detect auto-added areas.
* Add the new areas to the BBS.
* Copy the FILES.BBS made by Allfix to a compatible format.
* Update Allfix (when registered) so that it will recognize the new
addition to your BBS, eliminating the need to run FCOMP.
* Update Allfix (when registered) with the description pulled from
FILEBONE.NA or FILEBONE.NO, eliminating the need to run FIXUTIL
Describe.
* Supports PCBoard 15.x, Renegade (4.17 or later), Maximus 3.0,
Telegard 3.0, T.A.G 2.7, Spitfire, LoraBBS 2.40, and ProBoard.
*** NOTICE: REQUIRES ALLFIX 4.32 OR ALLFIX/2 1.XX (REGISTERED) ***
Auto-adding file areas is a registered feature of Allfix. I have no
control over this.
SETUP
-----
Put AUTOADD.EXE just about anywhere you want to, as long as you can
call it from a batch file.
AutoAdd requires certain switches and flags in Allfix to be setup up
in a compatible manner. If you can not or are unwilling to make these
changes, then AutoAdd is not for you.
Asetup switches that must be set:
In Asetup | Group Manager
All groups (that you expect to have areas added to) must have
Unique set to Yes. If not, MAJOR problems!
Because the setup is somewhat different for each BBS type, each
supported BBS type will be covered individually.
USING AUTOADD
-------------
AutoAdd is designed to be run from a batch file, but can be run
anytime. The call is:
AUTOADD <BBS type>
where <BBS type> =
5 - ProBoard
8 - PCBoard
9 - Spitfire
13 - TAG
14 - Renegade ?.??
18 - LoraBBS 2.40
19 - Telegard 3.0
22 - Maximus 3.0
Note that this is the same parameter you would use in a call to FCOMP.
Edit your AUTOADD.CFG to suit your system. AUTOADD.CFG *must*
reside in the same directory as AUTOADD.EXE. A sample configuration
file is included for each BBS type supported.
The call to AutoAdd is: AUTOADD <BBS type>.
AutoAdd will exit with an errorlevel of 1 if any file areas were
auto-added (if registered). This may require editing for your
system.
THE BATCH FILE
--------------
The way I call AutoAdd:
(snipped from my MAINT.001 batch file)
REM CHECK FOR TIC'S. RUN ALLFIX IF ANY
IF NOT EXIST D:\PCB\FIDO\INBOUND *.TIC GOTO PASSAF
D:
CD \ALLFIX
ALLFIX File -NoCrc
REM RUN AUTOADD
D:\PCB\AUTOADD 8 <- your BBS type here
IF NOT ERRORLEVEL 1 GOTO PASSAF
REM What ever you want here
REM This line is for PCBoard
MAKEIDX D:\PCB\GEN\INDEX1.PTH D:\PCB\GEN\INDEX1.IDX
:PASSAFF
ALLFIX Announce
AUTOADD.CFG
-----------
AUTOADD.CFG serves two purposes. It is used in conjunction with your
key file (once you get you key file), and to define the necessary
information AutoAdd needs to work with your particular setup. A great
deal of flexibility can be used here.
The first two lines contain the name you used to register AutoAdd
(case sensitive) and your registration code, in that order. The
remaining lines are either comments or configuration options. Please
see the explanation below for your BBS type. A sample configuration
file (individually archived) is provided for each supported BBS type.
There can be NO blank lines, nor should any line begin with a space.
- Comment lines.
There can be an unlimited number of comment lines (well, as long
as you have disk space). Each comment line must have a semicolon
(;) as the first character on the line. They are also limited to
250 total characters per line (include the semicolon).
- Configuration lines.
Each configuration line consists of a 4 letter key and one or
more fields. Each field is separated by one or more spaces.
Configuration lines my appear in any order. Unless specified,
only one occurrence (the last one) of each line will be honored.
Configuration lines are also limited to 250 total characters.
Configuration lines give you a great deal of flexibility in
defining what AutoAdd is to do and how it is to do it. Some are
common for all BBS types, while others define the defaults you would
like for such things as security levels, passwords, directory paths,
etc.
- Configuration lines common to all BBS types.
Key Description
--- -----------
AFIX This line has only one field, the path to your Allfix
directory.
LOGG This line has only one field, the path where you would like
AUTOADD.LOG written. If not present, AUTOADD.LOG will be
stored in the same directory as AUTOADD.EXE. If a filename
is specified, that file will be used.
- Configuration lines specific to BBS types.
PCBOARD 15.x
------------
Key Description
--- -----------
CNAM This line has one field, the path and name you entered in
PCBSETUP->File Locations->System Files & Directories->Name/Loc
of Conference Data. This is usually x:\PCB\MAIN\CNAMES, where
x is the drive letter.
DIRP This line has one field, the path you would like to store the
new DIRx style file in. When an area is auto-added, Allfix
creates a FILES.BBS file in the same path the files are
stored in. AutoAdd will always make a new file from the
FILES.BBS, naming it the same as the AreaTag for the new file
area and inserting the standard PCB DIRx header lines. This
line will allow you to specify another directory to store the
DIRx file created by AutoAdd. If not used, the new file will
be created in the same directory as the FILES.BBS file.
CONF This is the line that gives AutoAdd it's power. There can be
up to 256 of these line. The CONF line contains several
fields. Each field must be present and in the correct order.
- field 1: PCBoard conference (0 - 65567)
This is the PCBoard conference you would like to
be updated for an Allfix defined group.
- field 2: group(s) (0 - 255) (79 characters max)
AutoAdd allows you to assign a conference to each
file echo group defined in Allfix. This gives you
the flexibility to specify which FILEBONE.NA style
file goes with each file echo group and which
PCBoard conference files (DIR.LST and DLPATH.LST)
to update.
More than one group can be specified by separating each
group by a semicolon (;). Ex. 3;5;22
A range can be specified by separating the first and
last group in the range by a dash (-). Ex. 23-255
A combination can also be used. Ex 0;3-5;9-15
- field 3: Path and name of the FILEBONE.NA style file to use
for the group(s) defined in field 2. The file
defined here will be searched for the AreaTag of
the newly added area. The description for the
auto-added area as defined in the FILEBONE.NA
style file is then used to update file area
descriptions in PCBoard and Allfix.
- field 4: Path and name of the index.pth file to use. This
field allows you to define whether to update
DLPATH.LST or a text file for use with MAKEIDX.
Enter "NONE" (without quotes) not update anything.
Leave blank to use the DLPATH.LST for the
specified conference.
RENEGADE (versions later than 4.16)
-----------------------------------
Key Description
--- -----------
DATA This line has one field, the path to where FBASES.DAT and
EXTENDED.DAT are stored. This is usually x:\RENEGADE\DATA,
where x is the drive letter.
FBON This line has one field, the path and name of a FILEBONE.NA
style file. There can be more than one FBON line. Each will
be searched, in order, for the AreaTag of the auto-added file
area. The description for the auto-added area as defined in
the FILEBONE.NA style file is then used to update file area
descriptions in Renegade and Allfix.
DEFN This line has multiple fields and contains the defaults for
the newly added file area. This line is highly formatted. Use
care when you edit it.
- field 1: The path to use as the upload directory. Enter
"SAME" (without quotes) if you wish it to be the
same as the download path. 40 characters max
(including trailing "\". This is a Renegade
limit).
- field 2: Access, max files, archiver, and flags. Each
subfield is separated by a comma. All subfields
must be present. If a subfield is not used, the
comma must still be used as a place holder.
- subfield 1: Password. 12 characters max.
- subfield 2: Access (ACS). 20 characters max.
- subfield 3: Upload access (ULACS). 20 characters max.
- subfield 4: Download access (DLACS). 20 characters max.
- subfield 5: Maximum files allowed in this area. 1-65635.
- subfield 6: Archiver. 0 thru number of archivers defined in
Renegade. Warning: validity of this field is
not checked. 8 is the highest value Renegade
allows. 0 = None defined.
- subfield 7: Archive Comment. 1 - 3 as setup in Renegade.
- subfield 8: Credits required for download for each file.
This will be used in the new *.DIR file.
- subfield 9: Flags: C - CD-ROM
G - Gif Specs
D - Date Uploaded
S - Show Uploader Name
I - *.DIR in DLPATH
U - Unhidden
N - No Ratio
The I flag is honored by AutoAdd.
MAXIMUS 3.X
-----------
Key Description
--- -----------
DATA This line has one field, the path to MAX.PRM. This is
usually x:\MAX\, where x is the drive letter.
FBON This line has one field, the path and name of a FILEBONE.NA
style file. There can be more than on FBON line. Each file
will be searched, in order, for the AreaTag of the auto-added
file area. The description for the auto-added area as
defined in the FILEBONE.NA style file is then used to update
file area descriptions in Maximus and Allfix.
DEFN This line has two fields, the default upload path and access
name.
- field 1: The path to use as the upload directory. No check
is made for the validity of the path.
- field 2: Access name (level) for this file area. Enter the
<name> for the access level as defined in
ACCESS.CTL (Sysop, Demoted, etc).
TELEGARD 3.0
------------
Key Description
--- -----------
DATA This line has one field, the path to CONFIG.TG. This is
usually x:\TELEGARD\, where x is the drive letter.
FBON This line has one field, the path and name of a FILEBONE.NA
style file. There can be more than on FBON line. Each file
will be searched, in order, for the AreaTag of the auto-added
file area. The description for the auto-added area as
defined in the FILEBONE.NA style file is then used to update
file area descriptions in Telegard and Allfix.
DEFN This line has one field, but many subfields. It contains
the defaults to use when defining the new file area in
Telegard.
- field 1: Archiver, accesses, flags. Each subfield is
separated by a comma. Even if a subfield is not used, the
comma must be present as a place holder.
- subfield 1: Archiver (ZIP, ARJ, ARC, ZOO, etc).
- subfield 2: Sysop access.
- subfield 3: Access required to view the file list.
- subfield 4: Access required to see Uploader name.
- subfield 5: Access required to upload files.
- subfield 6: Access required to download files.
- subfield 7: Scan type - 0 - default on
1 - default off
2 - always.
- subfield 8: Flags - N - Noratio
V - Visible
G - GifSpecs
SPITFIRE
--------
Key Description
--- -----------
DATA This line has one field, the path to SFFAREA.DAT. This is
usually x:\SPITFIRE\, where x is the drive letter.
FBON This line has one field, the path and name of a FILEBONE.NA
style file. There can be more than on FBON line. Each file
will be searched, in order, for the AreaTag of the auto-added
file area. The description for the auto-added area as
defined in the FILEBONE.NA style file is then used to update
file area descriptions in Spitfire and Allfix.
DEFN This has three fields. The first two fields must be present,
while the last field my be left blank to use the defaults.
- field 1: Upload path. If you would like the upload path and
download path to be the same, enter "SAME" (without
the quotes). Maximum of 60 characters, including
the trailing "\".
- field 2: File area access level. 0 - 255.
- field 3: File area flags - E - User must have security level
equal to file area security
to upload or download.
Default is Equal to or
greater than.
S - Allow users with less
security to view files list.
Default is not to allow
viewing of the files list.
PROBOARD
--------
Key Description
--- -----------
DATA This line has one field, the path to FILECFG.PRO. This is
usually x:\PB\, where x is the drive letter.
FBON This line has one field, the path and name of a FILEBONE.NA
style file. There can be more than on FBON line. Each file
will be searched, in order, for the AreaTag of the auto-added
file area. The description for the auto-added area as
defined in the FILEBONE.NA style file is then used to update
file area descriptions in ProBoard and Allfix.
DEFN This line has several fields, each seperated by a comma. You
may define the defaults to use for the new file area here.
- field 1: File area security level
- field 2: File area access flags (A thru Z, 1 thru 6). Order
does not matter nor does case. You can make neat
words here, like AutoAdd115. In this case flags
ADOTU15 would be set.
- field 3: Maximum files allowed to DL.
- field 4: Maximum kilobytes allowed to DL.
- field 5: Do NOT show in TOPS.PB. T, true, True, TRUE all mean
"No. Do not show in TOPS.PB". Only the first letter
is checked.
- field 6: Free files. True or False (T or F). Same method as
field 5. Only the first letter is checked.
- field 7: Minimum age. 0 - 1000. Well, actually the range is
much greater, but I think the average life span is
well covered.
- field 8: Date format. 0 - MM/DD/YY
1 - DD/MM/YY
2 - YY/MM/DD
- field 9: Groups this area belongs to. "*" = All groups.
Otherwise, up to 4 groups may be listed, seperated by
a comma.
TAG 2.7
-------
Key Description
--- -----------
DATA This line has one field, the path to FBOARDS.DAT. This is
usually x:\TAG\DFILES\, where x is the drive letter.
FBON This line has one field, the path and name of a FILEBONE.NA
style file. There can be more than on FBON line. Each file
will be searched, in order, for the AreaTag of the auto-added
file area. The description for the auto-added area as
defined in the FILEBONE.NA style file is then used to update
file area descriptions in TAG and Allfix.
DEFN This line has several fields, each seperated by a comma. You
may define the defaults to use for the new file area here.
- field 1: Password. 15 characters max.
- field 2: Access. 0 - 255.
- field 3: Access level to see Uploader name. 0-255.
- field 4: No Ratio flag. "True" or "T" for "Yes, no ratio.",
or "False" or "F" for "No, ratio active."
- field 5: Group this file area belongs to. 0-127.
- field 6: AR flag. @..Z. Only one flag allowed.
- field 7: Use "FILES" as the filename for the files list.
"True" or "T", "False" of "F". Defaults to "False.
Do not use FILES as the filename for the files
list."
All fields must be seperated by a comma. All fields must be
present. This means that even if a field is not used, a comma
must be used as a place holder.
LORABBS 2.40
------------
Key Description
--- -----------
DATA This line has one field, the path to SYSFILE.DAT. This is
usually x:\LORA\, where x is the drive letter.
FBON This line has one field, the path and name of a FILEBONE.NA
style file. There can be more than on FBON line. Each file
will be searched, in order, for the AreaTag of the auto-added
file area. The description for the auto-added area as
defined in the FILEBONE.NA style file is then used to update
file area descriptions in LoraBBS and Allfix.
DEFN This line has several fields, each seperated by a comma. You
may define the defaults to use for the new file area here.
- field 1: Minimum area number. This is the lowest area
number AutoAdd will use when adding new file areas.
The new area number will always be the highest in
the file area database.
- field 2: Upload path. This is a required field.
- field 3: Free files area, True (T) or False (F).
- field 4: Exclude this area from global searchs, True or
False.
- field 5: Minimum level required for this area. 1 - Twit,
2 - Disgrace,
3 - Limited,
...,
13 - Hidden
- field 6: Access flags. 0-9 and A-V. Order does not matter.
- field 7: File area access level. 1 - Twit.....
- field 8: File area flags. 0-9 and A-V.
- field 9: Download access. 1 - Twit.....
- field 10: Download flags. 0-9 and A-V.
- field 11: Upload access. 1 - Twit....
- field 12: Upload flags. 0-9 and A-V.
All fields must be seperated by a comma. All fields must be
present. This means that even if a field is not used, a comma
must be used as a place holder. Fields 5 - 12 are optional.
They will all default to Twit privilages and no flags. No
fields may be skipped. If not used or you desire the default,
you must use a comma as a place holder for fields preceding the
field you do use.
REGISTRATION
------------
Registration is $5.00 (US). Registration will enable the updating of
Allfix. See AUTOADD.REG for further information.
EVALUATION KEY
--------------
A 30 day evaluation key can be obtained by calling the support BBS
(The Spy's Nest, see below), logging on with the name and password of
AUTOADD. After logging on, you should be in Conference 4. Type EVAL
and follow the on-screen instructions.
CONTACTING THE AUTHOR
---------------------
I can be reached at:
The Spy's Nest 1-904-458-0982/1-904-457-9111 (V.34/VFC)
FIDO 1:3612/386 (or 1:3612/386.1)
I also hang out in ALLFIX_HELP and supported BBS type support echos.
WARRANTY & DISCLAIMER
---------------------
There are no warranties, express or implied, for unregistered copies
of AutoAdd. The author will NOT be held liable for any direct,
indirect, incidental, or consequential damage resulting from the use
of this program. Your use of this program constitutes your AGREEMENT
to this disclaimer and your release of the author from any form of
liability.
Registered copies of AutoAdd are warranted to perform as described
in this documentation. In the event AutoAdd does not perform as
described, then the author will elect to either rectify the problem or
refund the amount of the registration paid, provided notification is
received within 30 days of registration.
All brand and product names are Copyrighted (C) material, Trademarks
(tm) or Registered (R) Trademarks of their respective holders:
Allfix Harald Harmes
PCBoard Clark Developement Co.
Renegade Cott Lang
Maximus Lanius Corporation
Telegard Tim Strike
SpitFire Buffalo Creek Software
ProBoard Philippe Leybaert